Skip to main content
TrustRadius
Sparx Systems Enterprise Architect

Sparx Systems Enterprise Architect

Overview

What is Sparx Systems Enterprise Architect?

Enterprise Architect is the flagship architecture management platform from global, Australian-headquartered company Sparx Systems.

Read more
Recent Reviews
Read all reviews
Return to navigation

Pricing

View all pricing

Professional

$229

On Premise
per license

Corporate

$299

On Premise
per license

Unified

$499

On Premise
per license

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Demos

Shape Scripts in Sparx Systems Enterprise Architect

YouTube

eaDocX Rolling Demo

YouTube
Return to navigation

Product Details

What is Sparx Systems Enterprise Architect?

Sparx Systems Enterprise Architect Technical Details

Deployment TypesOn-premise
Operating SystemsWindows, Linux, Mac
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(44)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Based on user feedback, here are the most common recommendations for the software:

  1. Consider seeking assistance from a consultant during the introduction and initial setup of the software.
  2. Look for a product that provides more flexible and complex documentation based on the software's repository, as the default document generator is considered too basic.
  3. Improve guidance for baselining and version control within the software to help users effectively manage changes and versions of their design artifacts.

These recommendations focus on seeking external expertise, enhancing documentation capabilities, and improving baselining and version control guidance to optimize the software's functionality.

Attribute Ratings

Reviews

(1-3 of 3)
Companies can't remove reviews or game the system. Here's why
Jean Bernard Mathias, CDMP, CBIP,TOGAF,SOA Arcitura,ITIL,CBAP | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
I used Sparx Systems Enterprise Architect to deliver services to clients. It enables our Enterprise Architecture work.
  • Easy to get started
  • Easy to share content
  • It supports TOGAF and UML.
  • It requires knowledge of Enterprise Architecture.
  • You need a proper plugin to deliver Enterprise Architecture.
Sparx Systems Enterprise Architect is well suited for a client that does not have any Enterprise Architecture or Business Process and that needs to get started. The information is available in Excel and you can get started by importing the artifacts in the proper structure. Word documents can also be imported by using the proper plugins. It can be used as a jump-start for a team of five people that can share a common repository.
  • Implementation without management support will be shelfware
  • It should be used for decision making based on facts.
  • There should be a process to enable validation of contents using proper governance.
I have tried Essential Project. In terms of price, it is open-source and it helped to get started. The price of extraction information was more expensive than Sparx with a plugin called BEASI.
The support team of Sparx EA, based in Australia, is always willing to help and give direction.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Sparx Systems Enterprise Architect's typical usage scenarios comprise the capturing of business requirements, of more detailed use cases and scenarios that mimic required business situations and processes in a comprehensive way that is understood by business stakeholders as well as IT analysts. Business requirements can be then further translated to business logic (models, algorithms, process flows/workflows, business data objects, and other artifacts) that are linked to a high level as well as low-level ICT design (application logic, integration models, data models, etc.). The main reason and advantage for putting all the above into one IT solution (Enterprise Architect) is to provide a set of business and IT models, that are interrelated and any change to components such as process, data entity, integration service, business requirement, etc., can be traced to all other components. This would be the best practice - to have a tool that keeps track of any change you plan to do to your systems and helps indicates impacted components and relations. In practice, there are several obstacles to reaching this best usage practice.
  • Enables recording and managmenet of all changes/requirements on ICT solutions.
  • Improves transparency of relations among models.
  • Helps to manage complexity of documentation.
  • Supports well team collaboration (server version with shared database) and allows to manage user access rules.
  • Essential tool for enterprise, application, integration and data architects.
  • Is well thought through in respect to user experience, it is easy to work in the tool for both, business occasional users as well as seasoned IT analysts.
  • Management of change requests or business requirements is much better implemented in JIRA or Confluence, there is an option to integrate EA artifacts with Confluence/JIRA specifications, via third party solution, in my experience this works one-directional, from EA to Confluence. Maybe there exists other solutions with a full synchronization. The result today is that you can share e.g. architectures designed in Enterprise Architect in Confluence.
  • Model governance, especially by working on large scale projects with lots of people, requires double checking of any major change you want to do to the models, e.g. deleting of a particular item/component. Some feature to make deleting "more safe" would be nice.
Enterprise Architect can be used to capture business requirements, design and management of all successive models, algorithms, process flows/workflows, design of business data objects and other artifacts. The strong point is the ability to link the items in all models with each other, the more time the analysts and designers "invest" into making nice and clearly defined models, the higher the future pay-off by any successive changes to the systems.

Enterprise Architect is not a good tool for capturing rather unstructured business requirements, use e.g. Confluence or other solutions instead. EA should comprise the extracted models with very little unstructured information.

Management of the changes process should not be done in Enterprise Architect, rather use JIRA/Confluence or similar.
  • No immediate impact, rather long-term benefits, especially when companies launch large restructuring projects, unbundling (as seen in Telecommunications, Utilities etc.) this tool accelerates the analytical tasks. It can save literally man-years of work in any large company, with complex ICT landscape.
  • No negative impact, the cost of the tool is negligible, compared to the benefits.
BiZZdesign represents a different new concept to enterprise architecture, its gravity center is not technical modelling, but rather a view on capturing the whole end-user experience or customer journey. It also allows to grasp areas as internal company capabilities, required for adoption/changes and operation of the solution, uses the same Archimate modelling language. This solution is in my opinion a new generation enabling to not only design the solutions, but also manage the whole application portfolio with respect to capabilities and requirement parameters.
The solution is well complemented by external addons from third parties.
Alastair Rennie | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Sparx Systems Enterprise Architect (EA) is being used to model all of the layers of operation within the business. This starts with the highest level of business modeling. Major business processes are modeled, then the more detailed processes within the business areas. This then drills down to the systems supporting the business functions then on to the systems architecture that delivers the systems.

This is used to ensure that a complete map of operational processes maps to a supported system and that architecture update plans are consistent with software upgrades and hardware lifecycles.
  • Descriptions of business processes, actors, actions, outcomes and outputs
  • Mapping of all systems to business processes
  • Collation of all architectural elements that comprise individual systems
  • Needs someone that is very conversant with business modelling terminology
EA is well suited to modeling business processes. This allows operational architects to design or re-design the business processes with a view to interaction between operational elements.

Modelling of systems architecture can be very self-absorbing with no real business benefit. A clear scope of outcomes is required before starting an EA project.
  • EA has provided a very positive impact on business understanding
  • EA has allowed us to map clearly our physical and logical architecture, and to allow us to plan replacement systems and platforms
I have used Orbus iServer. EA compares well with iServer, though iServer is a very useful cloud service that allows access from many locations. Licensing costs of iServer are very favourable compared to EA for a larger number of users.
Return to navigation